chore(ci): bump lerna
& add provenance config
#1541
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
This PR introduces the necessary changes to publish packages to npmjs.com together with a provenance statement backed by Sigstore.
Specifically, the PR:
lerna
(package used to publish) to version6.6.2
which is the version that introduced support for the featurepublish-npm
job, according to the npm docs on the topic: https://docs.npmjs.com/generating-provenance-statementsNPM_CONFIG_PROVENANCE=true
, which according to the npm docs & the lerna maintainers should instruct the script to publish a provenance statement.Related issues, RFCs
Issue number: closes #1436
Checklist
Breaking change checklist
Is it a breaking change?: NO
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.